Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1608

reference
455-tree-1
name
1608
tree-preservation-order

undefined

455-tpo-1
uprn
address-text
point
POINT (-1.044722 50.883595)
geometry
MULTIPOLYGON (((-1.044538 50.883576,-1.044546 50.883612,-1.044572 50.883645,-1.044612 50.883671,-1.044663 50.883688,-1.044720 50.883694,-1.044778 50.883689,-1.044829 50.883673,-1.044871 50.883647,-1.044898 50.883615,-1.044907 50.883579,-1.044899 50.883543,-1.044874 50.883510,-1.044833 50.883484,-1.044782 50.883467,-1.044725 50.883460,-1.044668 50.883466,-1.044616 50.883482,-1.044575 50.883507,-1.044548 50.883540,-1.044538 50.883576)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL